Improved documentation for signing/encryption keys. #986
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #985
These are improvements to the documentation regarding signing and encryption keys.
This is still WIP as I need to investigate howtmp_cert_file
andtmp_cert_key
are being used. I determined that this is the path where the keys are generated, but I am not sure what the generated keys are being used for.I investigated
Entity
,SecurityContext
andCryptoBackend
to gather information on this, but someone can review this and see if I made a mistake.Kind regards